Method of taking a computer architecture representation and generating manufacturing computer systems contained in a specification

ABSTRACT

Techniques and a system for creating a vendor independent computer language and compiling the language into an architecture specification language allowing for taking a source data stream (file, WSDL, XML) and passing thru a language parser, populating a storage medium with a plurality of technical inputs and vendor technical specifications for generic technologies and probable technologies required for desired architectures generated by the language parser, and optimizing the inputs and creating relationships between technologies and groups of technologies and storing results in the storage medium.

FIELD

The disclosed subject matter relates to methods of taking a computer architecture representation and generating manufacturing methods capable of manufacturing the computer systems contained in the specification. The matter disclosed herein also includes an enhanced means of executing those applications and causing the specified systems to be built on demand.

DESCRIPTION OF THE RELATED ART

The traditional method is for an engineer to take a high-level design specification and for the engineer to research and use vendor specific documentation of commands and his individual knowledge and experience to determines the necessary equipment, creates a Bill of Material, creates a low level design, and creates implementation instructions. To deploy the system, for each system to be deployed, the engineer takes the implementation instructions executes the commands in the implementation instructions necessary to create the systems. He then creates operating instructions for operating the systems and executes those to place the system under operational management. An alternate method is for an engineer to code the commands he would execute into a service catalog or a provisioning tool. The problem that this creates is that the engineer is manually mapping the high-level design to the individual commands necessary to implement that high-level design and then either manually executing those commands as placing those commands in a service catalog or provisioning tool. If the end user decides to transition from one technology to another they have to have this mapping recreated potentially by a completely different engineer with the appropriate knowledge of the commands on the desired technology. A significant amount of the information gathered and generated for the initial implementation is not retained and usable for subsequent designs.

SUMMARY

Techniques here disclosed include a method and system for generating a computer architecture representation in a reusable syntax and grammar. As a result the matter disclosed herein also includes an enhanced means of creating artifacts such as high-level design documents, bills of materials and traditional drawings.

The present matter disclosed herein provides a method of generating a computer architecture representation in a reusable syntax and grammar, wherein a plurality of language definitions that include at least a first language definition for technical specifications and attributes. This information is typically submitted by an engineer, and comes in the form of multiple specifications and may include vendor technical specifications, best practices, and corporate best practices.

Technical Specifications for applications may include, but are not limited to, details such as memory required, disk space required. Technical specifications for operating systems may include, but are not limited to, hardware limitations such as required physical memory, processor type. Industry best practice details may include, but are not limited to, that although the vendor recommends a certain amount of memory for an application, the industry best practice is two times that amount.

The term “technical specification” is understood herein as any data that is provided by an engineer or manufacturer, detailing technology including but not limited to operating system requirements, application requirements, or hardware requirements. As an exemplary scenario, a technical specification for Windows® 2012 Server® may specify minimum processor: 1.4 Ghz 64-bit processor, minimum ram: 512 MB, minimum disk: 32 GB.

In accordance with an embodiment of the matter disclosed herein the method provides a second language definition for business details and attributes. This information is typically provided by the user and includes but not limited to goals, decisions, constraints, site details and user details. A decision may include, but is not limited to, a selection of a particular vendor. Business details may include, but are not limited to, number of locations, size of locations, and users at locations.

The term “business details” and “business attributes” is understood herein as any data that is provided by a user that is specific to their business environment. As an exemplary scenario, a business attribute may specify to use the industry best practice over the vendor specification.

In accordance with a further embodiment of the matter disclosed herein, the method provides third language definition supplementary details and attributes. This information is custom data that can be customer or implementation dependent. An example supplemental detail may be able to be to a specific vendor or technology bias.

The term “supplementary details” and “supplementary attributes” is understood herein as any data that is provided by a user as custom data. As an exemplary scenario, a user may specify a operating system or manufacturer bias, such as Microsoft® is a preferred vendor. Algorithms selected at runtime may use this supplemental data for decisions.

In an embodiment of the matter disclosed herein, the method provides for parsing and performing semantic grammar analysis for each of the language definitions that consist of reading each line of input, parsing and performing semantic grammar analysis of attributes of the specification, elements or lines, element lists/groups and attributes of the list/group, individual elements or lines and attributes of the elements, and finally individual lines or elements within a list/group and any attributes of that element and produce an intermediate representation as reusable individual elements and attributes. In some embodiments of the matter disclosed herein, the method may include a means of deconstructing these specifications into reusable elements, which provides the advantage that elements may be reused in a plurality of designs.

In an embodiment of the matter disclosed herein, the method has a means for dynamically compile and generate an architectural specification based on user selected data, the produced intermediate representation, and an algorithm selected at run time that consists of reading each input variable and passing those variables to the specified algorithm. The algorithm processes the individual elements and attributes based on the defined algorithm. The output of the selected algorithm is then passed to the compiler to generate the architecture specification in a specific language definition.

The term “architecture representation” is understood herein as a data structure for storing and representing the data contained in a high-level design in a generic reusable way.

In accordance with a further embodiment of the matter disclosed herein, the method has a means for dynamically compile and generate an architectural specification based on user selected data, the produced intermediate representation, supplemental details and attributes, and an algorithm selected at run time that consists of reading each input variable and passing those variables to the specified algorithm. The algorithm processes the individual elements and attributes based on the defined algorithm. The output of the selected algorithm is then passed to the compiler to generate the architecture specification in a specific language definition.

In accordance with a further embodiment of the matter disclosed herein, the method provides a means for dynamically generating industry standard technical documents from a generated architecture specification.

In another aspect the matter disclosed herein is directed to a system implementing the above described language specifications, methods and compiler mechanism.

Embodiments of the matter disclosed herein have the advantage that different architectures are capable of being generated rapidly based on a broader set of technical and engineering inputs than the conventional methods. In accordance with an embodiment of the matter disclosed herein, the system further provides means for receiving a source data stream of input information from the user. Memory means allow for a data structure instantiating code segment that establishes a storage record in memory, as well as for storing technical input records, business input records, relationships, and architecture specification language representation. A processor means operates for parsing and performing semantic grammar analysis for each of the language definitions, as well as recording parsed results to the storage medium. The processor means further enables executing a selected optimization function to optimize and create relationships and saving the results to the storage medium. The disclosure includes executing a compilation function to compute and create an architectural representation in the specified syntax and grammar. In accordance with a further embodiment of the matter disclosed herein, the system further provides means for receiving a source data stream of input information from the user. Memory means enable a data structure instantiating code segment that establishes a storage record in memory and for storing technical input records, business input records, relationships, supplemental details and attributes, and architecture specification language representation. A processor means operates parsing and performing semantic grammar analysis for each of the language definitions including supplemental details and attributes, recording parsed results to the storage medium, executing a selected optimization function to optimize and create relationships and save results to the storage medium, as well as executing a compilation function to compute and create an architectural representation in the specified syntax and grammar.

These and other advantages of the disclosed subject matter, as well as additional novel features, will be apparent from the description provided herein. The intent of this summary is not to be a comprehensive description of the claimed subject matter, but rather to provide a short overview of some of the subject matter's functionality. Other systems, methods, features, and advantages here provided will become apparent to one with skill in the art upon examination of the following FIGUREs and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the accompanying claims.

BRIEF DESCRIPTIONS OF THE DRAWINGS

The features, nature, and advantages of the disclosed subject matter will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:

FIG. 1 provides a UML use case diagram being illustrative of an embodiment of a method of the matter disclosed herein;

FIG. 2 is a UML activity diagram being illustrative of the conventional workflow for creating a high-level design;

FIG. 3 is a UML activity diagram being illustrative of an embodiment of a method of submitting a specification for use as part of the body of reusable information;

FIG. 4 is a UML sequence diagram being illustrative of an embodiment of a method of processing or deconstructing a specification;

FIG. 5 is a UML sequence diagram being illustrative of an embodiment of a method of the matter disclosed herein;

FIG. 6 is a UML component diagram being illustrative of an embodiment of a computer system of the matter disclosed herein.

APPENDIX 1 shows exemplary grammar for a specification file;

APPENDIX 2 shows exemplary grammar for a specification file; and

APPENDIX 3 shows a shows exemplary implementation of the grammar in APPENDIX 1 but in XML as an alternative format.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 1 is illustrative of an embodiment where an actor element 106 shows the information flow from the engineer into the method represented as element 100. FIG. 1 also shows other actors that may interface with the method in an exemplary embodiment.

FIG. 2 is illustrative of an embodiment where an actor 102, 104, or 106 from FIG. 1 makes a business decision to deploy a particular application or technology 120. An actor 102, 104 or 106 from FIG. 1, takes that business decision as input and make a series of technical decisions 122. The actor must make a decision 124 if the deployment is a new deployment or a deployment over an existing “Brown Field.” If the deployment is a new deployment 126, then a new set of requirements are developed. If there is an existing deployment the actor must make a decision 128 to reuse existing requirements. If the actor chooses not to reuse existing requirements then the deployment is treated as a new deployment 126 and a new set of requirements are developed. If the actor chooses to reuse the existing requirements then an audit of the legacy deployment must be performed 130 and the requirements documented 132. The actor reviews the resulting requirements 134 for acceptance 138. If they do not meet the business decisions 120 and technical decisions 122 then they are not accepted the requirements are revised 136. If the requirements are accepted the actor generates by hand a high-level design document 140 based on his individual knowledge and experience. An actor then takes this high-level design, and for each requirement contained in the high-level design 142 he determines the necessary equipment, creates a Bill of Material 146, creates a low level design 150, and creates implementation instructions 148. To deploy the system, for each system to be deployed 144, the actor takes the implementation instructions 148 and executes them 152 to create the systems. He then creates operating instructions 156 for operating the systems and executes those 154 to place the system under operational management.

FIG. 3 is illustrative of an embodiment where an actor submits a specification for use by the exemplary embodiment as part of the body of reusable information. Elements 160 thru 168 represent an interaction with the user interface of the system. An actor 106 from FIG. 1 attempt to access the system 160. If authentication 162 fails the access is denied 164. If authentication 162 is successful the main page 166 is displayed. The user selects select a specification file 168 and selects a specification file for use 170. The user then submits the file 172 for use. Lexical and syntactical analysis is performed on the submitted data to determine if the data is a valid structure and grammatical syntax 174. If the lexical or syntactical analysis fails there is a language or structure problem 176. If the lexical and syntactical analysis passes then the file is parsed 178 and the information retained for later use. A positive confirmation is provided of acceptance of the specification 180.

FIG. 4 is illustrative of an embodiment where a user 200 interacts with the system via the Submit Specification boundary 202. The Create New Specification control 204 mediates between the Submit Specification boundary 202 and the Specification entity 206 and orchestrates the behavior including but not limited to the parsing of the lists, elements and execution of the algorithms.

FIG. 5 is illustrative of an embodiment where an actor interacts with the system via the System boundary 212. The Language Parser control 214 receives the inputs from the System boundary 212 and processes the inputs. The Language Parser control 214 loops thru the specification and extracts the inputs. If supplemental data is present in the source data stream the Language Parser control 214 loops thru the specification and extracts supplemental data and attributes. Once the inputs have been extracted the Language Parser control 214 persists the inputs to Persistence actor 222 via the persistInputs( ) message 220. The Language Parser control 214 then passes control to the Optimization Processor control 226 to performOptimizations( ) 228 of inputs and createRelationships( ) 230. The Optimization Processor control 226 then persistOptimizations( ) 232 and persistRelationships( ) to persist the data to the Persistence actor 222. Once the Optimization processor control 226 has persisted its data it passes control to the Compile processor control 236. The Compile Processor control 236 produces either a Architecture Specification entity 240 or a Manufacturing Application entity 244 depending on the embodiment.

FIG. 6 is illustrative of an embodiment where a source data stream object 252 is submitted to the computer System 250 via a computer network for processing. The Language Parser component 254 is invoked and uses the system processor to calculate and extract the inputs from the data stream. The Language Parser component 254 persists its data to the Persistence component 256 which may be a database or system memory data structure. The Optimization Processor component 258 is invoked to retrieve the inputs from the Persistence component 256 and uses the system processor to execute an optimization algorithm and create necessary relationships. The Optimization Processor component 258 persists its data to the Persistence component 256. The Compiling Processor component 260 is invoked to retrieve the optimized inputs and relationships from the Persistence component 256 and uses the system processor to execute a compilation algorithm to generate either an Architecture Specification artifact 262 or a Manufacturing Applications artifact depending on the embodiment. In a further embodiment of the system the Manufacturing Processor component 266 will be invoke to use the system processor to execute the Manufacturing Applications artifacts 264 to create the Deployed Systems artifact 268.

To facilitate the processing of specifications a new grammar and syntax may be required. The listing in APPENDIX 1 and APPENDIX are exemplary grammar for a specification file that may be used as inputs to the methods described in FIG. 3 and FIG. 4. The listing in APPENDIX 3 shows a possible implementation of the grammar in APPENDIX 1 but in XML as an alternative format.

A method of consuming a high-level design or computer architecture representation and generating manufacturing methods capable of manufacturing the computer systems contained in the specification, comprising the steps of taking a source data stream (file, WSDL, XML) passing thru a parser. The process includes populating a storage medium with a plurality of application programming interfaces (api's), commands, and vendor implementation specifications for specific technologies required for architectures generated by the language parser, as well as optimizing the inputs and creating relationships between commands and groups of commands or api's required to implement portions of the architecture and storing results in the storage medium.

The disclosed method further includes the steps of further populating the storage medium with supplemental attributes. The may employ a compiling algorithm to retrieve inputs and a high-level design stored in an architectural specification language from the storage medium and produce a plurality of system manufacturing applications. Also, the method may employ a compiling algorithm to retrieve from the storage medium a high-level design stored in an architectural specification language and inputs and/or supplemental attributes, and produce a plurality of system Manufacturing applications.

Another embodiment of the present disclosure includes a system for consuming a high-level design or computer architecture representation and generating manufacturing applications capable of manufacturing the computer systems contained in the specification. This embodiment may include a language parser communicating with the storage medium and coupled to a computer network for parsing vendor implementation specifications, api's, and commands into individual inputs and value pairs and records those inputs to the storage medium. An optimization processor may communicate with the storage medium and coupled to a computer network for optimizing parsed inputs and creates relationships and records those inputs to the storage medium. Moreover, a language parser may communicate with the storage medium and coupled to a computer network for parsing computer architecture representations and records those inputs to the storage medium. Then, a compiling processor communicating with the storage medium and coupled to a computer network for retrieving inputs from the storage and generating a plurality of system manufacturing applications, while a manufacturing server coupled to a computer network and having memory and processor stores and executes the manufacturing applications. The server preferably conducts a manufacturing transaction with a user and either delivering the manufacturing applications to the user or executing the manufacturing applications directly. Such a system embodiment may further include a language parser communicating with the storage medium and coupled to a computer network for parsing supplemental attributes into individual inputs and value pairs and records those inputs to the storage medium.

Yet a further embodiment of the present disclosure may include a computer program embodied on a computer-readable medium for creating a vendor implementation computer language. The computer program embodiment may include a data structure for instantiating code segment that establishes a storage record in memory. Such a data structure may include a command/api identifier, as well as a plurality of separate command or api records, each maintaining a pointer to the command/api identifier. Here compiling algorithm may include instructions for deconstructing a high-level design, identifying commands to execute in order to create the architecture represented, and constructing and compiling manufacturing applications necessary to execute identified commands.

This embodiment contemplates the use of a data structure instantiating code segment that establishes a storage record in memory having, an architecture specification identifier, and a plurality of technical input records and business input records, each maintaining a pointer to said architecture specification identifier. Here, a compiling algorithm provides instructions for deconstructing the computer architecture representation, identifying commands to execute in order to create the architecture represented, and constructing and compiling manufacturing applications necessary to execute identified commands.

The processing features and functions described herein for generating a computer architecture representation in a reusable syntax and grammar. The disclosed subject matter provides an enhanced means of creating artifacts such as high-level design documents, bills of materials and traditional drawings that may be implemented in various manners. Moreover, the process and features here described may be stored in magnetic, optical, or other recording media for reading and execution by such various signal and instruction processing systems. The foregoing description of the preferred embodiments, therefore, is provided to enable any person skilled in the art to make or use the claimed subject matter. Thus, the claimed subject matter is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

APPENDIX 1 Example Specification Language Structure %token STRING Specification: attribute_element requirement_element   | attribute_element requirement_element_list requirement_element   ; attribute_element: element TYPE literal   ; requirement_element_list: requirement_element   | requirement_element_list requirement_element   ; requirement_element: element   ; element:   VALUE literal literal:   STRING

APPENDIX 2 Example Architecture Specification Language Structure %token STRING Architecture specification: attribute_element deployment_element | attribute_element_list deployment_element | attribute_element deployment_element_list deployment_element | attribute_element_list deployment_element_list attribute element deployment element ; attribute_element_list: attribute_element | attribute_element_list attribute_element ; attribute_element: element TYPE literal ; deployment_element_list: deployment_element | deployment_element_list deployment_element ; deployment_element: DEPLOYMENT literal | DEPLOYMENT literal TYPE literal ; provider_element_list: provider_element | provider_element_list provider_element ; provider_element: PROVIDER literal | PROVIDER literal TYPE literal ; hypervisor_element_list: hypervisor_element | hypervisor_element_list hypervisor_element ; hypervisor_element: HYPERVISOR literal | HYPERVISOR literal TYPE literal ; os_element_list: os_element | os_element_list os_element ; os_element: OS literal | OS literal TYPE literal ; application_list: application_element | application_element_list application_element ; application_element: APPLICATION literal | APPLICATION literal TYPE literal ; element: NAME literal | NAME literal TYPE literal literal: STRING

APPENDIX 3 Example XML Specification <TechnicalSpecification XMLns:xsi=http://www.w3.org/2001/ XMLSchema-instancexsi:noNamespaceSchemaLocation=”TS.xsd”>    <RequirementGroup>       <Value>Windows Server 2007</Value>       <Attribute>          <Type>Sequence</Type>          <Value>1</Value>       </Attribute>       <SubRequirementGroup>          <Requirement>             <Value>Memory</Value>             <Attribute>                <Type>Sequence</Type>                <Value>1</Value>             </Attribute>             <Attribute>                <Type>Minimum</Type>                <Value>2048</Value>             </Attribute>             <Attribute>                <Type>Recommend</Type>                <Value>4096</Value>             </Attribute>          </Requirement>          <Requirement>             <Value>Disk</Value>             <Attribute>                <Type>Sequence</Type>                <Value>2</Value>             </Attribute>             <Attribute>                <Type>Minimum</Type>                <Value>8G</Value>             </Attribute>             <Attribute>                <Type>Recommend</Type>                <Value>20G</Value>             </Attribute>          </Requirement>       </SubRequirementGroup>    </RequirementGroup> </VendorTechnicalSpecification> 

1. A system comprising: a first language parser communicating with a storage medium and coupled to a computer network for parsing vendor implementation specifications, application program interfaces and commands into individual inputs parser in reference to a grammar that includes a requirement of memory having attributes of sequence, minimum and recommended and a requirement of disk having attributes of sequence, minimum and recommended and value pairs and records the inputs to the storage medium; an optimization processor communicating with the storage medium and coupled to a computer network for optimizing parsed inputs and creates relationships and records those inputs to the storage medium; a second language parser communicating with the storage medium and coupled to a computer network for parsing computer architecture representations and records those inputs to the storage medium; a compiling processor communicating with the storage medium and coupled to a computer network for retrieving inputs from the storage and generating a plurality of system manufacturing applications; and a manufacturing server coupled to a computer network and having memory and processor for storing and executing the system manufacturing applications.
 2. The system of claim 1, further comprising: a third language parser communicating with the storage medium and coupled to a computer network for parsing supplemental attributes into individual inputs and value pairs and records those inputs to the storage medium.
 3. The system of claim 1, further comprising: a deconstuctor communicating with the second language parser for deconstructing the vendor implementation specifications, application program interfaces and commands into reusable elements.
 4. The system of claim 3, further comprising: a component communicating with the deconstuctor for reusing the reusable elements in a plurality of system manufacturing applications.
 5. The system of claim 1, further comprising: a deconstuctor communicating with the second language parser for deconstructing the vendor implementation specifications, application program interfaces and commands into intermediate reusable elements.
 6. The system of claim 5, further comprising: a component communicating with the deconstuctor for reusing the intermediate reusable elements in a plurality of system manufacturing applications.
 7. A non-transitory computer medium comprising: a data structure instantiating code segment that establishes a storage record in memory having a command/application programming interface identifier; a data structure instantiating code segment that establishes a storage record in memory having: an architecture specification identifier; a plurality of technical input records and business input records, each maintaining a pointer to the architecture specification identifier; and computer instructions for: deconstructing a representation of a computer architecture; and identifying commands to execute in order to create the computer architecture through constructing and compiling manufacturing applications necessary to execute identified commands; a plurality of separate command or application programming interface records, each maintaining a pointer to the command/application programming interface identifier; computer instructions for: deconstructing a high-level design; identifying commands to execute in order to create the architecture represented; and constructing and compiling manufacturing applications necessary to execute identified commands.
 8. The non-transitory computer medium of claim 7, further comprising: computer instructions for deconstructing the representation of a computer architecture into reusable elements.
 9. The non-transitory computer medium of claim 8, further comprising: computer instructions for reusing the reusable elements in a plurality of system manufacturing applications.
 10. The non-transitory computer medium of claim 7, further comprising: computer instructions for deconstructing the representation of a computer architecture into reusable intermediate elements.
 11. The non-transitory computer medium of claim 10, further comprising: computer instructions for reusing the reusable intermediate elements in a plurality of system manufacturing applications.
 12. The non-transitory computer medium of claim 7, the architecture specification identifier further comprising: the high level design stored in a architectural specification language, the architectural specification language comprising a grammar that includes a requirement of memory having attributes of sequence, minimum and recommended and a requirement of disk having attributes of sequence, minimum and recommended.
 13. An apparatus comprising: a receiver of a source data stream of a representation of a computer architecture; a language parser of the representation of a computer architecture that operates in reference to a grammar that includes a requirement of memory having attributes of sequence, minimum and recommended and a requirement of disk having attributes of sequence, minimum and recommended; populating a storage medium with a plurality of application programming interfaces, commands, and vendor implementation specifications for specific technologies required for architectures generated by the language parser; and creating relationships on the storage medium between the commands and groups of the commands or the application programming interfaces in accordance with the specification and that are required to implement portions of the computer architecture.
 14. The apparatus of claim 13, further comprising: a deconstructor of the representation of a computer architecture into reusable elements.
 15. The apparatus of claim 14, further comprising: using the reusable elements in a plurality of system manufacturing applications.
 16. The apparatus of claim 13, further comprising: a deconstructor of the representation of a computer architecture into reusable intermediate elements.
 17. The apparatus of claim 14, further comprising: using the reusable intermediate elements in a plurality of system manufacturing applications. 